security: remove code that runs automatically when the project is opened or built - #119
Merged
Conversation
- strip-gitignore: .gitignore
restored eslint.config.js (restored to its 1893-byte version) Each restored file keeps the content it had before the payload was appended.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
⚠ PARTIAL remediation for
Ndevu12/RichTextEditorby StayAwakeBot Security Sentinel — this branch applies what is provably safe but is NOT a clean tree (see below).Changes applied
strip-gitignore—.gitignore🚨 Still infected — confirmed indicators NOT auto-fixed (manual action required)
1 confirmed finding(s) could not be safely auto-remediated and remain in this tree. Do NOT merge this as a completed fix — the security gate stays red. Resolve each, then re-run
saw fix --pr:8acf0688f2—evil-merge-loader(evil-merge):Worm payload smuggled via this merge COMMIT (a history finding, not a file edit; files: .gitignore, eslint.config.js). ʼsaw fixʼ never rewrites history — it breaks clones/forks/tags. If the payload is gone from your working tree the tree is clean but the commit persists; verify no fork/tag still shi⚠ Still needs review (not auto-fixed)
These are suspicious (heuristic) matches — possibly a legitimate inlined asset/minified file, possibly a payload the confirmed signatures didn't name. Review each; allowlist if legitimate, or remove if not.
evil-merge—222e2c763cwhitespace-concealment—eslint.config.js:66oversized-config-line—eslint.config.js:66obfuscated-source-file—eslint.config.jsOriginals are recoverable from git history. Evil-merge findings (if any) are reported separately and need a manual history rewrite.
Review and merge if correct. This is a single rolling PR — re-runs update it rather than opening duplicates.
Extended beyond the automatic fix. The original change removed what could be stripped safely.
This branch now also handles the files the automatic pass left alone:
the real configuration is kept, not deleted
Verified afterwards: no file on this branch still matches any campaign marker.
Worth knowing: merging this cleans this branch only. Other branches in this repository may carry
the same files and should be checked separately.